BERT, Group 50

Use Case UC5: Manage Employees

Revision History: current version v1

Primary Actor: BERT Administrator

Stakeholders and interests:

- Administrator: Wants to be able to maintain the Employee Subsystem through viewing, adding, modifying and deleting Employees from the system.

-Employee: Wants up-to-date and correct personnel information to be stored on persistent storage.

-Management: Wants up-to-date and correct information about its employees to be stored on persistent storage.

Preconditions:

1. The Administrator has been successfully logged in to the BERT Management subsystem.
2. The Administrator's access priveleges have been verified.
3. The Employee booking information is available for interrogation.

Success Guarantee (Post conditions):

1. Employee information has been viewed, added, modified or deleted from the Employee Subsystem.

Main Success Scenario (or Basic Flow):

1. System presents the Administrator with the options to view, add, modify or delete an Employee.
2. Administrator chooses to View an Employee and submits choice to system.
3. System receives Administrators chosen function and begins execution.
   1. If "Add an Employee" is chosen, extension 3a is executed.
   2. If "Modify an Employee" is chosen, extension 3b is executed.
   3. If "Delete an Employee" is chosen, extension 3c is executed.
4. System retrieves all Employee information.
5. System presents Administrator with a view of all Employees registered with the System.
6. Administrator exits Use Case.

Actor repeats steps 1-3 until indicates done.

Extensions (or Alternative Flows):

3a. Administrator wants to "Add an Employee".

1. System requests that the Administrator enters the Employee information.
2. Administrator enters the Employee information.
3. Administrator submits the information to the system.
4. System receives new Employee information.
5. System stores the new Employee information on persistent storage.
6. System presents the Administrator with a message confirming successful update.

Actor repeates steps 2-3 until indicates done.

3b. Administrator wants to "Modify an Employee".

1. System presents Administrator with a view of all Employees currently registered with the System..
2. Administrator selects which Employee is to be modified and submits request to system.
3. System presents Administrator with the facility to edit current information.
4. Adminstrator enters modifications.
5. Administrator submits a request for the Employee information to be updated.
6. System receives updated information.
7. System stores the updated Employee information on persistent storage.
8. System presents the Administrator with a message confirming successful update.

Actor repeats steps 2-5 until indicates done.

3c. Administrator wants to "Delete an Employee".

1. System presents Administrator with a view of all Employees currently registered with the System.
2. Administrator selects an Employee to be deleted.
3. Administrator submits request for the Employee to be deleted.
4. System receives request.
5. System removes the Employee information from persistent storage.
6. System presents the Administrator with a message confirming successful update.

Actor repeates steps 2-3 until indicates done.

Special Requirements:

-

Technology and Data Variations List:

n/a

Frequency of Occurrence:

Occurrence on an ad-hoc basis.

Open Issues:

-